Dynomotion

Group: DynoMotion Message: 6794 From: himykabibble Date: 2/22/2013
Subject: KMotion 430l Consol Broken?
Tom,

Last night, before calling it a night, I installed 430l. This morning, I fired up the machine, and started working, and immediately found my pendant misbehaving badly - missing some actions, mis-interpreting others. The code on my side has not changed in probably 9 months. I exited my app, started KMotion, killed all threads, and started just the pendant code on thread 2. I un-commented one line in my code that does a printf to display the message received from the pendant to the console (it uses RS232 to communicate with the KFlop. It will typically display 3-10 such messages, then KMotion simply go out to lunch. At this point, the console is dead - even a "Version" command gets no result. If I dis-connect and re-connect the board, the disconnect is not even acknowledged with the little pop-up dialog. from KMotion. If I exit KMotion, then re-start it, then all is well once again, until the pendant sends a few more messages, then the failure repeats. It is re-starting KMotion that gets things working - I don't have to do anything to the board - no reset, no re-starting threads. Everything on the board seems to be working fine throughout.

I backed off the firmware to 430j, and everything is working normally again. So, it appears there is something broken in the KMotion console code in 430l.

Regards,
Ray L.
Group: DynoMotion Message: 6795 From: Tom Kerekes Date: 2/22/2013
Subject: Re: KMotion 430l Consol Broken?
Hi Ray,

Yes you are correct.  Somehow the Console Window lost the scroll bar (probably when we added the new "Clear" screen button). 

If you hit "Clear" to free up more space the messages appear to resume.

We will make a fix ASAP.   Sorry about that.

Regards
TK

Group: DynoMotion Message: 6796 From: himykabibble Date: 2/22/2013
Subject: Re: KMotion 430l Consol Broken?
Tom,

Thanks. No harm done.

BTW - Also found the real source of the problem I was having with random exceptions. It turned out to be a hardware problem. One of the relay boards was somehow injecting noise into the KFlop. I managed to find a way to make it happen fairly easily using KMotion by just toggling I/Os. So that is not fixed. I can't explain how it managed to very consistently manifest in my app as a failure in one of the Persist read functions, but it seems happy now!

BTW - A friend of mine has just had some custom KFlop BOBs made. They plug directly onto the KFlop and pickup all the connectors. Everything is buffered, and there's a fair amount of configurability. We should have the first ones smoke tested in the next week. This is going to seriously reduce the rats nest of wiring I have right now to get all the I/Os to/from the KFlop.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>
> Yes you are correct.  Somehow the Console Window lost the scroll bar (probably when we added the new "Clear" screen button). 
>
>
> If you hit "Clear" to free up more space the messages appear to resume.
>
> We will make a fix ASAP.   Sorry about that.
>
> Regards
> TK
>
>
>
> ________________________________
> From: himykabibble <jagboy1964@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, February 22, 2013 11:09 AM
> Subject: [DynoMotion] KMotion 430l Consol Broken?
>
>
>  
> Tom,
>
> Last night, before calling it a night, I installed 430l. This morning, I fired up the machine, and started working, and immediately found my pendant misbehaving badly - missing some actions, mis-interpreting others. The code on my side has not changed in probably 9 months. I exited my app, started KMotion, killed all threads, and started just the pendant code on thread 2. I un-commented one line in my code that does a printf to display the message received from the pendant to the console (it uses RS232 to communicate with the KFlop. It will typically display 3-10 such messages, then KMotion simply go out to lunch. At this point, the console is dead - even a "Version" command gets no result. If I dis-connect and re-connect the board, the disconnect is not even acknowledged with the little pop-up dialog. from KMotion. If I exit KMotion, then re-start it, then all is well once again, until the pendant sends a few more messages, then the failure
> repeats. It is re-starting KMotion that gets things working - I don't have to do anything to the board - no reset, no re-starting threads. Everything on the board seems to be working fine throughout.
>
> I backed off the firmware to 430j, and everything is working normally again. So, it appears there is something broken in the KMotion console code in 430l.
>
> Regards,
> Ray L.
>
Group: DynoMotion Message: 6797 From: himykabibble Date: 2/22/2013
Subject: Re: KMotion 430l Consol Broken?
Tom,

There has to be something wrong beyond a missing scroll bar in KMotion.exe.... My pendant was messing up badly, even with my app, when KMotion wasn't even running. But all the same code works fine with 430j.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>
> Yes you are correct.  Somehow the Console Window lost the scroll bar (probably when we added the new "Clear" screen button). 
>
>
> If you hit "Clear" to free up more space the messages appear to resume.
>
> We will make a fix ASAP.   Sorry about that.
>
> Regards
> TK
>
>
>
> ________________________________
> From: himykabibble <jagboy1964@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, February 22, 2013 11:09 AM
> Subject: [DynoMotion] KMotion 430l Consol Broken?
>
>
>  
> Tom,
>
> Last night, before calling it a night, I installed 430l. This morning, I fired up the machine, and started working, and immediately found my pendant misbehaving badly - missing some actions, mis-interpreting others. The code on my side has not changed in probably 9 months. I exited my app, started KMotion, killed all threads, and started just the pendant code on thread 2. I un-commented one line in my code that does a printf to display the message received from the pendant to the console (it uses RS232 to communicate with the KFlop. It will typically display 3-10 such messages, then KMotion simply go out to lunch. At this point, the console is dead - even a "Version" command gets no result. If I dis-connect and re-connect the board, the disconnect is not even acknowledged with the little pop-up dialog. from KMotion. If I exit KMotion, then re-start it, then all is well once again, until the pendant sends a few more messages, then the failure
> repeats. It is re-starting KMotion that gets things working - I don't have to do anything to the board - no reset, no re-starting threads. Everything on the board seems to be working fine throughout.
>
> I backed off the firmware to 430j, and everything is working normally again. So, it appears there is something broken in the KMotion console code in 430l.
>
> Regards,
> Ray L.
>
Group: DynoMotion Message: 6802 From: Tom Kerekes Date: 2/23/2013
Subject: Re: KMotion 430l Consol Broken?
Hi Ray,

Here is a new test version where the Console Screen shouldn't lock up.

http://dynomotion.com/Software/KMotion430m.exe

I can't think of any other changes that would relate to your Pendant.  Can you locates something specific that isn't working?

Regards
TK




Group: DynoMotion Message: 6803 From: himykabibble Date: 2/23/2013
Subject: Re: KMotion 430l Consol Broken?
Tom,

I'll try again with this new version later today, but so far, simply reverting to 430j, with absolutely no changes on my side has everything working perfectly once again. From the behavior I was seeing, it seemed like the pendant thread was not getting called as often as it should, or the RS232 was not working correctly - response was very sluggish, and it would completely miss button presses, and other actions. I've never seen anything remotely like that before.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>
> Here is a new test version where the Console Screen shouldn't lock up.
>
> http://dynomotion.com/Software/KMotion430m.exe
>
> I can't think of any other changes that would relate to your Pendant.  Can you locates something specific that isn't working?
>
> Regards
> TK
>
>
>
>
>
>
> ________________________________
> From: himykabibble <jagboy1964@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, February 22, 2013 8:01 PM
> Subject: [DynoMotion] Re: KMotion 430l Consol Broken?
>
>
>  
> Tom,
>
> There has to be something wrong beyond a missing scroll bar in KMotion.exe.... My pendant was messing up badly, even with my app, when KMotion wasn't even running. But all the same code works fine with 430j.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Ray,
> >
> > Yes you are correct.  Somehow the Console Window lost the scroll bar (probably when we added the new "Clear" screen button). 
> >
> >
> > If you hit "Clear" to free up more space the messages appear to resume.
> >
> > We will make a fix ASAP.   Sorry about that.
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: himykabibble
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, February 22, 2013 11:09 AM
> > Subject: [DynoMotion] KMotion 430l Consol Broken?
> >
> >
> >  
> > Tom,
> >
> > Last night, before calling it a night, I installed 430l. This morning, I fired up the machine, and started working, and immediately found my pendant misbehaving badly - missing some actions, mis-interpreting others. The code on my side has not changed in probably 9 months. I exited my app, started KMotion, killed all threads, and started just the pendant code on thread 2. I un-commented one line in my code that does a printf to display the message received from the pendant to the console (it uses RS232 to communicate with the KFlop. It will typically display 3-10 such messages, then KMotion simply go out to lunch. At this point, the console is dead - even a "Version" command gets no result. If I dis-connect and re-connect the board, the disconnect is not even acknowledged with the little pop-up dialog. from KMotion. If I exit KMotion, then re-start it, then all is well once again, until the pendant sends a few more messages, then the failure
> > repeats. It is re-starting KMotion that gets things working - I don't have to do anything to the board - no reset, no re-starting threads. Everything on the board seems to be working fine throughout.
> >
> > I backed off the firmware to 430j, and everything is working normally again. So, it appears there is something broken in the KMotion console code in 430l.
> >
> > Regards,
> > Ray L.
> >
>
Group: DynoMotion Message: 6805 From: himykabibble Date: 2/23/2013
Subject: Re: KMotion 430l Consol Broken?
Tom,

So far, 430m looks fine. Thanks!

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>
> Here is a new test version where the Console Screen shouldn't lock up.
>
> http://dynomotion.com/Software/KMotion430m.exe
>
> I can't think of any other changes that would relate to your Pendant.  Can you locates something specific that isn't working?
>
> Regards
> TK
>
>
>
>
>
>
> ________________________________
> From: himykabibble <jagboy1964@...>
> To: DynoMotion@yahoogroups.com
> Sent: Friday, February 22, 2013 8:01 PM
> Subject: [DynoMotion] Re: KMotion 430l Consol Broken?
>
>
>  
> Tom,
>
> There has to be something wrong beyond a missing scroll bar in KMotion.exe.... My pendant was messing up badly, even with my app, when KMotion wasn't even running. But all the same code works fine with 430j.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Ray,
> >
> > Yes you are correct.  Somehow the Console Window lost the scroll bar (probably when we added the new "Clear" screen button). 
> >
> >
> > If you hit "Clear" to free up more space the messages appear to resume.
> >
> > We will make a fix ASAP.   Sorry about that.
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: himykabibble
> > To: DynoMotion@yahoogroups.com
> > Sent: Friday, February 22, 2013 11:09 AM
> > Subject: [DynoMotion] KMotion 430l Consol Broken?
> >
> >
> >  
> > Tom,
> >
> > Last night, before calling it a night, I installed 430l. This morning, I fired up the machine, and started working, and immediately found my pendant misbehaving badly - missing some actions, mis-interpreting others. The code on my side has not changed in probably 9 months. I exited my app, started KMotion, killed all threads, and started just the pendant code on thread 2. I un-commented one line in my code that does a printf to display the message received from the pendant to the console (it uses RS232 to communicate with the KFlop. It will typically display 3-10 such messages, then KMotion simply go out to lunch. At this point, the console is dead - even a "Version" command gets no result. If I dis-connect and re-connect the board, the disconnect is not even acknowledged with the little pop-up dialog. from KMotion. If I exit KMotion, then re-start it, then all is well once again, until the pendant sends a few more messages, then the failure
> > repeats. It is re-starting KMotion that gets things working - I don't have to do anything to the board - no reset, no re-starting threads. Everything on the board seems to be working fine throughout.
> >
> > I backed off the firmware to 430j, and everything is working normally again. So, it appears there is something broken in the KMotion console code in 430l.
> >
> > Regards,
> > Ray L.
> >
>